Repository navigation
chore(node): run CI and @types/node on Node.js 26 - #86
Conversation
Node.js 26 became the Active LTS line on 2026-10-28. The Tests and Release workflows now run it, and @types/node follows it at ^26, as CLAUDE.md requires. The engines range doesn't change. npm install also moves the lockfile's root version from 1.9.0 to 1.10.0, which the Version Packages PR left behind. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Why
Node.js 26 became the Active LTS line on 2026-10-28. This PR moves CI and the dev types from Node.js 24 to 26.
What changed
@types/nodegoes from^24to^26(26.6.6), because CLAUDE.md keeps it on the Node.js major that CI runs.Scope
enginesrange stays^22.18.0 || ^24.11.0 || >=26.0.0, so nothing changes for consumers on Node.js 22 or 24.versionmoves from 1.9.0 to 1.10.0.changeset versionbumps onlypackage.json, so the Version Packages PR left the lockfile behind, and the next release will do the same.Blast Radius
Only contributors and CI see this change. The published package doesn't change, because
dist/built on Node.js 24 and on Node.js 26 is byte-identical. The next real publish runs npm 11.20.0, which ships with Node.js 26.13.1.Verification
npm run lintpasses, andnpm testpasses 286 tests plus 1 expected failure with 100% line coverage.npm run test:e2erun passed 293 tests and failed the Chromium trackpad swipe test, which also flakes on master. That test and the Firefox reduced-motion test each passed 20 of 20 repeats on Node.js 24.20.0 and on 26.13.1.diff -rfinds no difference betweendist/built on Node.js 24.20.0 and on 26.13.1.🤖 Generated with Claude Code
Summary by CodeRabbit